docs: describe Security and logs experiences in the Classic solution view (#8975) - #9253

… setting (elastic#303878)

## Summary

Adds the `discover:enableSolutionProfilesInClassic` advanced setting to
the Advanced settings reference. The setting was introduced in elastic#296406
and is missing from `docs/reference/advanced-settings-space.yml`. It
controls whether **Discover** switches to the Observability and Security
experiences when you use Classic navigation. It is on by default,
requires a page reload, and does not appear in serverless projects.

Part of elastic/docs-content#8975. The pages that describe the behavior
are in
[elastic/docs-content#9253](elastic/docs-content#9253),
which updates the [Discover
documentation](https://www.elastic.co/docs/explore-analyze/discover).

### Identify risks

None. This is a docs-only change to a reference YAML file.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>

…view (#8975) (#9253)

## Summary

This PR is part of #4898 and is stacked on #9014. It targets the #9014
branch until that PR merges. It addresses #8975 with the following
changes:

- **`solutions/security/investigate/discover-security.md`**: The
**Access the Security Discover experience** section said the Security
experience activates only from the Security solution view. It now also
covers Classic solution view spaces from 9.6: which data views and
queries trigger it, that mixed data keeps the default experience, and
how to turn it off.
- **`solutions/observability/logs/discover-logs.md`**: Adds a section
that lists the integrations that get the logs experience in the Classic
solution view, and what keeps the default experience. The note about the
Observability solution view points to it.
- **`explore-analyze/discover/discover-get-started.md`**: The
Observability, Security, and Classic solution view lists in
**Context-aware experiences** are now one table of where you open
**Discover** against the experiences you get. It adds the Classic
solution view and the Elasticsearch solution view and projects. Numbered
notes under the table hold the conditions that the cells link to.

The new **Contextual profiles in Classic navigation** reference entry
was added in elastic/kibana#303878, and the pages here link to it.

## Resolves

Closes #8975

## Differences from the issue

- The issue suggested listing the exact Security index patterns. This PR
describes the data in plain words, such as alerts and endpoint events,
because the list is long and changes with the product.
- The issue did not list the logs page. This PR adds the integration
list there, because its note said the Observability solution view was
required for a contextual logs experience.

## Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this
contribution?
- [x] Yes
- [ ] No

Tool(s) and model(s) used: Claude Code with Claude Sonnet 5.5. I checked
the claims against the Kibana source.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>